Oracle ADF End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Oracle ADF versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Oracle ADF 12.2.1.x (12c) is supported until December 31, 2026, its end-of-support date. It is also the next Oracle ADF version to reach end of life. 4 of 6 tracked Oracle ADF versions are past end of life; the most recent to reach it, 11gR2 (11.1.2.x), did so on December 31, 2018. The full Oracle ADF lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 10gR3 (10.1.3.x) | 10.1.3 | — | Jun 30, 2014 | Jun 30, 2017 Extended support (ended) |
4485 days past EOL | EOL |
| 11gR1 (11.1.1.x) | 11.1.1 | — | Dec 31, 2018 | Dec 31, 2021 Extended support (ended) |
2840 days past EOL | EOL |
| 11gR2 (11.1.2.x) | 11.1.2 | — | Dec 31, 2018 | Dec 31, 2021 Extended support (ended) |
2840 days past EOL | EOL |
| 12.1.x (12c) | 12.1 | — | Dec 31, 2017 | Dec 31, 2019 Extended support (ended) |
3205 days past EOL | EOL |
| 12.2.1.x (12c) | 12.2.1.4.0 | — | Dec 31, 2026 | Dec 31, 2027 Extended support |
82 days remaining | Warning |
| 14.1.x (14c) | 14.1 | — | Dec 31, 2030 | Dec 31, 2033 Extended support |
1543 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/oracle-adf)
Oracle ADF lifecycle status — the real story
Oracle Application Development Framework (ADF) is the Java EE framework that ships with Oracle JDeveloper and underpins many Oracle applications. Oracle's Fusion Middleware Lifetime Support Policy (edition effective April 13, 2026) gives ADF 10gR3, 11gR1 and 11gR2 their own rows under Application Development Tools and says 12c releases "will follow the overall Lifetime Support policies for Fusion Middleware 12c"; the 14.1.x row lists JDeveloper and Application Development Framework in its footnote. Dates are the last day of Oracle's month ("unless otherwise noted, each stage of support is provided through the last day of the month"). Mobile Application Framework is a separate exception in the same policy and is not covered here.
CISA's Known Exploited Vulnerabilities catalog lists CVE-2022-21445, a deserialization flaw in the ADF Faces library that allows unauthenticated remote code execution; Oracle's advisory names 12.2.1.3.0 and 12.2.1.4.0 as the affected supported versions.
Oracle ADF release and support pattern
Of the 6 release lines tracked, 4 are past end of life and 2 are still within support. The next scheduled end of life is 12.2 on December 31, 2026 — 82 days from this build. The longest-supported line currently published is 14.1, to December 31, 2030. Upstream also publishes an extended-support phase for 6 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Oracle ADF security intelligence
CISA KEV history: Oracle ADF is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2024-09-18. Derived from CISA's live catalog at every build.
What does Oracle ADF end of life mean for your organization?
When a version of Oracle ADF reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Oracle ADF should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Oracle ADF reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Oracle ADF versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Oracle ADF has 4 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Oracle ADF is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."